Skip to content
Discussion options

You must be logged in to vote

Ah, what a great feature request! I'll try to get that into the next release (should be next week). Thanks!

I'll add a new API called empty_bucket which will clear it out of data and/or files, but leave the bucket itself intact.

Note that in order to call the API from within a job, you'll need an API key. After creating it and assigning privileges (it'll need the edit_buckets priv), you can store the key in a secret vault, and assign it to the event, so it'll show up as an environment variable (e.g. XYOPS_API_KEY). Also, the full URL to the current xyOps conductor server is always available inside each job as the JOB_BASE_URL env var.

Example invocation from shell:

curl -fsSL -H "X-API-Key: 

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@jhuckaby
Comment options

@greenaar
Comment options

Answer selected by greenaar
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants