- Le plus récent
- Le plus de votes
- La plupart des commentaires
I think you will need to commit the devfile.yaml to the repository , then stop & kill the Cloud9 instance/dev envronment.
A completely newly created DevEnvironment should then use the devfile.yaml - did you try that?
As @Lockhead mentioned, commit your changes and then start the Dev Environment. Let us know if the issue persists.
From our documentation, https://docs.aws.amazon.com/codecatalyst/latest/userguide/devenvironment-devfile.html
We recommended that you edit the devfile in a supported IDE and then update your Dev Environment, but you can also edit the devfile from the root of the source repository in CodeCatalyst. If you edit the devfile in a supported IDE, you must commit and push your changes to the source repository or create a pull request so a team member can review and approve the devfile edits.
Hi there, yes, if I make the changes to the devfile and then start a new environment, the changes get picked up.
I realise that devfiles are probably not going to change very often, so it's just a minor friction point that we have to create a new environment rather than being able to 'refresh' an existing environment.
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- Réponse acceptéedemandé il y a un an
- AWS OFFICIELA mis à jour il y a 3 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 3 ans
Hi. yes as mentioned above, I've got it working that when creating a new environment it picks up the devfile. It would just be good if there was some mechanism where we could force an environment to pick up a refreshed devfile - but it's a minor pain point.