Fix shell compatibility issues in production deployment workflow #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The production deployment workflow was failing due to shell compatibility issues between
/usr/bin/shand bash-specific syntax in thesync-secrets.shscript.Problem
The workflow was encountering errors like:
This occurred because:
/usr/bin/shfor script executionsync-secrets.shscript uses bash-specific features ([[,${!var},=~) that are not supported in POSIX shellSolution
Updated both deployment workflows (production and staging):
shell: bashdirective to all run stepsbash scripts/sync-secrets.shto/usr/bin/bash scripts/sync-secrets.shEnhanced the sync-secrets.sh script:
#!/usr/bin/env bashto#!/usr/bin/bashfor reliabilityBefore:
After:
Testing
The fixes ensure:
Fixes #3.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.