Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

kubectl-run pipe tries to write unmodifiable artifact

I am trying to change our kubernetes yaml files so that they are generated by a tool.  This tool creates the files and they are saved as artifacts and then passed to the step that runs the kubectl-run pipe.  The kubectl-run pipe tries to modify these files and fails with the error 

Traceback (most recent call last):
File "/pipe.py", line 121, in <module>
pipe.run()
File "/pipe.py", line 112, in run
self.handle_apply()
File "/pipe.py", line 77, in handle_apply
self.update_labels_in_metadata(template_file, labels)
File "/pipe.py", line 33, in update_labels_in_metadata
with open(template, 'w') as template_file:
PermissionError: [Errno 13] Permission denied: 'kubernetes/foo-service-staging-deployment.yml'

It appears that this is caused by the pipe attempting to add some metadata about the bitbucket build, etc.  This metadata is nice but not necessary.  It would be better if the pipe would wrap the write in a try/catch so that  the pipe doesn't fail if it can't be added.

1 answer

1 accepted

0 votes
Answer accepted

@cgray i see one of possible root cause that you may set the owner while working with files or file that you will pass as RESOURCE_PATH variable.

If that helps you, try executing such lines before running a pipe:

chmod +rw $RESOURCE_PATH (adding -R option if resource path is a folder, not a single file).

Looking forward to see your feedback. In the meantime we'll try to reproduce this edgecase.

Thank you for raising question.

Regards, Galyna

Yes that works.  Thank you for your help.

Like Galyna Zholtkevych likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

875 views 16 11
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you