Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix copy-state usage for brooklyn-karaf #258

Merged
merged 1 commit into from
Jun 21, 2018

Conversation

aledsage
Copy link
Contributor

In brooklyn classic, one could run brooklyn copy-state .... This is not supported in brooklyn karaf.

Instead, the REST api can be used. This PR updates the docs to show how to use it.

Please first review/merge apache/brooklyn-server#972, to fix this REST api for usage in karaf!


tar --exclude '*/backups/*' -czvf $BACKUP_FILENAME $TEMP_DATA_DIR
# For s3cmd installation see http://s3tools.org/repositories
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know it's not directly related to this PR, but we should switch to recommending the official AWS CLI now that it's mature and stable:

# For AWS CLI installation see https://aws.amazon.com/cli
aws s3 cp $BACKUP_FILENAME s3://mybackupbucket
rm $BACKUP_FILENAME

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nakomis I opened a PR for this: #260

@nakomis
Copy link
Contributor

nakomis commented Jun 21, 2018

One minor comment, other than that LGTM

@asfgit asfgit merged commit 4d417bb into apache:master Jun 21, 2018
asfgit pushed a commit that referenced this pull request Jun 21, 2018
Fix copy-state usage for brooklyn-karaf

In brooklyn classic, one could run `brooklyn copy-state ...`. This is not supported in brooklyn karaf.

Instead, the REST api can be used. This PR updates the docs to show how to use it.

Please first review/merge apache/brooklyn-server#972, to fix this REST api for usage in karaf!
asfgit pushed a commit that referenced this pull request Jun 21, 2018
Use the official AWS CLI instead of s3cmd

Based on this comment: #258 (comment)

Note: I checked the docs and this is the only place where we suggested to use `s3cmd`
@aledsage aledsage deleted the fix-copy-state branch June 25, 2018 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants