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
This will make it easier to diagnose and debug implicit issues where someone defines the env variables twice, once in the yaml or local shell, and again from the sub config+arm template outputs.
kurtzeborn
added
Central-EngSys
This issue is owned by the Engineering System team.
and removed
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
labels
Jan 23, 2023
…es for local use (#5242)
Follow up fix related to discussion on Azure/azure-sdk-for-net#33262
- Make name generation simpler and more consistent across test resource scripts (found a bug where remove-testresources.ps1 would not have worked for nested service directories like data/aztables)
- Use a short hash for resource names deployed locally, to avoid edge cases where a long service directory or username causes resource names to be too long for validation (e.g. keyvault).
- Fix issue with `EnvironmentVariables` ref getting updated from the parameters when splatting in CI mode and polluting the env variable outputs on subsequent runs in the same shell.
- Add more warning logging if we're overwriting environment variables, for #4931Fixes#4931
This will make it easier to diagnose and debug implicit issues where someone defines the env variables twice, once in the yaml or local shell, and again from the sub config+arm template outputs.
CC @christothes
The text was updated successfully, but these errors were encountered: