1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
To correctly upload the content of my_file_name.py, you should use the file:// prefix with the --file-content parameter, which tells the AWS CLI to read the content from the specified file. Your command should look like this:
aws codecommit put-file \
--repository-name MY_REPOSITORY \
--branch-name main \
--file-content file://path/to/my_file_name.py \
--file-path GUI/my_file_name.py \
--parent-commit-id a7ddbb7a99dd37c9e2c5fe378eba1187xxxxxxxx \
--name "Name" \
--email "my-email" \
--commit-message "Adding file from EC2 instance."
Contenus pertinents
- demandé il y a 6 mois
- demandé il y a un an
- demandé il y a un an
AWS OFFICIELA mis à jour il y a un an- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 9 mois
This is bit odd. It works for transferring a file from the home directory but when, I try pushing from the /opt directory, it's generating the error "Error parsing parameter '--file-content': Unable to load paramfile file:///opt..."
You may need to use sudo to elevate access to /opt Or try file://opt/filename.py
Sorry but with the storm, I forgot to follow up on this matter. I had tried both options on Friday (even switching to superuser with $ sudo su) but was getting other errors. I'm accepting the answer because this seems to be the best we can do at this point, but this issue should probably be elevated either to the CLI or CodeCommit Teams.