Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pac solution sync does not bring down environment variables into the source #997

Open
scottdurow opened this issue Aug 15, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@scottdurow
Copy link

scottdurow commented Aug 15, 2024

Describe the bug
When using pac solution sync, environments are not always synced and missing from the solution unpacked source.

This may be related to #477

To Reproduce
Steps to reproduce the behavior:

  1. Create an empty solution
  2. Clone the solution using pac solution clone
  3. Add a new string environment variable to the solution.
  4. Sync the solution using pac solution sync - the string environment will be synced
  5. Add a Boolean (Yes/No) environment variable
  6. Sync the solution again using pac solution sync - the bool environment is not present in the solution source
  7. Repeat Steps 5 and 6 until the issue happens - it sometimes seems to sync and sometimes doesn't.

Expected behavior
Environment variables should always be synced correctly.

Additional context
Using version 1.33.5+g1621296 of PAC

@scottdurow scottdurow added the bug Something isn't working label Aug 15, 2024
@scottdurow scottdurow changed the title pac solution sync does not bring down Boolean Yes/No environment variables into the source pac solution sync does not bring down environment variables into the source Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant