You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have just tried to use "Publish To Environment" to push changes to our 'PROD' environment.
Since that environment is not defined in the environment list & I have no environment secret defined, it takes me through "device login" path. Very smooth and handy
Then, it deploys artifacts to the environment. All good here.
But, when my CICD process runs, it suddenly picks this PROD environment and tries to deploy to it. I never asked for it, and I have no setup for it in my AL go settings.
The reason for this is that GitHub creates the environment under environments when you run Publish to environment to that.
excludeEnvironments as Maria says or using the DeployToSRSPROD, setting "ContinuousDeployment": false should solve this.
It is counterintutive though that an environment used to publish once gets picked up for continuous deployment automatically - will investigate what we can do about that.
I think this should be fixed by only allowing continuous deployment to environments, where a authcontext secret exists in either GitHub or the KeyVault. If no authcontext secret exists, the deployment will fail anyway and we shouldn't try in the first place.
Hey @freddydk,
I have just tried to use "Publish To Environment" to push changes to our 'PROD' environment.
Since that environment is not defined in the environment list & I have no environment secret defined, it takes me through "device login" path. Very smooth and handy
Then, it deploys artifacts to the environment. All good here.
But, when my CICD process runs, it suddenly picks this PROD environment and tries to deploy to it. I never asked for it, and I have no setup for it in my AL go settings.
My Al-go-settings file looks like this:
Best Regards,
Gintautas
The text was updated successfully, but these errors were encountered: