Skip to content
This repository has been archived by the owner on Jun 19, 2024. It is now read-only.

Ability to specify object namespace in fragments #1699

Closed
jcechace opened this issue Aug 29, 2019 · 0 comments · Fixed by #1703
Closed

Ability to specify object namespace in fragments #1699

jcechace opened this issue Aug 29, 2019 · 0 comments · Fixed by #1703
Assignees
Labels
size/s Small

Comments

@jcechace
Copy link

As a developer, I want the ability to deploy different object into different namespaces.
That means the plugin should apply objects according to namespace specified in fragments.

Currently what happens if fragment contains a namespace different than the specified working namespace is this error

Failed to execute goal io.fabric8:fabric8-maven-plugin:4.3-SNAPSHOT:resource-apply (default-cli) on project test-openshift: Failed to update ConfigMap from openshift.yml. io.fabric8.kubernetes.client.KubernetesClientException: Namespace mismatch. Item namespace:debezium-mysql. Operation namespace:debezium.. ConfigMap(apiVersion=v1, binaryData=null, data={log4j.properties=kafka.logs.dir=logs
@rohanKanojia rohanKanojia self-assigned this Sep 4, 2019
rohanKanojia added a commit to rohanKanojia/fabric8-maven-plugin that referenced this issue Sep 11, 2019
namespace inside resource fragments should be given more priority over
default namespace
@rohanKanojia rohanKanojia added the size/s Small label Sep 11, 2019
rohanKanojia added a commit that referenced this issue Oct 3, 2019
namespace inside resource fragments should be given more priority over
default namespace
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
size/s Small
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants