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
Currently, when you have the required environment variables set, it will override the hubspot.config.yml settings. This can be a problem if the variables are set unbeknownst to the user and commands are attempted to be run using the hubspot.config.yml settings.
We should look into adding an option to commands to explicitly use the environment variable config like hs watch --use-env or something similar. Research some different options for this.
The text was updated successfully, but these errors were encountered:
This would be a potentially breaking change for users right? Since it would now use the hubspot.config.yml instead of their env vars unless they add this flag. We'll need to communicate it and major bump again
Yes, the change here has the potential to break a setup that is currently using the environment variables because it would require adding the option flag. We have not publicly released/documented/announced this feature so I think we are in the clear here as we make the option required prior to the official release
Currently, when you have the required environment variables set, it will override the
hubspot.config.yml
settings. This can be a problem if the variables are set unbeknownst to the user and commands are attempted to be run using thehubspot.config.yml
settings.We should look into adding an option to commands to explicitly use the environment variable config like
hs watch --use-env
or something similar. Research some different options for this.The text was updated successfully, but these errors were encountered: