ca-scribner / bundle-kubeflow-management

Tools for managing the Canonical Charmed Kubeflow bundle

bundle-kubeflow-management

Tools for managing the Canonical Charmed Kubeflow bundle

sync_charmstore_credentials.yaml

This workflow automates updating charmstore/charmcraft credentials on all repos listed in sync_charmstore_credentials.yaml. To add new managed repos, add them to the list in the yaml file.

To enable access to update the secrets of the above repos, a github PAT that has access to all repos must be stored here as a secret.

To refresh the credentials for repos, do:

1. Get recent credentials, for example using:

(charmstore)

charm login && cat ~/.go-cookies

(charmcraft (requires charmcraft > 1.3.1)

charmcraft login --export /tmp/charmcraft.credentials && echo "Copy the key below this line" && cat /tmp/charmcraft.credentials && rm /tmp/charmcraft.credentials

2. Insert above credentials into this repo's CHARMSTORE_CREDENTIAL/CHARMCRAFT_CREDENTIALS secret (Settings->Secrets)
3. Run the workflow (Actions->Sync Charmstore Credentials->Run workflow (button at the top right of the workflow runs list)). To do a dryrun, leave dryrun=True. To actually push secrets to all repos, set dryrun=False.

bundle-kubeflow-management's Issues

some test issue

Bug Description

What did I do

What did I observe

What did I expect

To Reproduce

adad

Environment

How are you running juju?

What track/channel have you deployed your charm from?

Versions of other applicable components:

Relevant log output

juju debug-log --replay -i mycharm

Paste your logs here, this'll be expandable!  But leave a line of whitespace between the ` ``` ` and the opening/closing `<details>`
The backticks format this like code, probably making it more readable

kubectl logs my-charm-workload

Paste your logs here, this'll be expandable!  But leave a line of whitespace between the ` ``` ` and the opening/closing `<details>`
The backticks format this like code, probably making it more readable

Or, render shorter logs as code directly

using backticks

Additional context

No response

Share repos list across workflows/tasks

Make a text file list of the repositories (maybe separate lists for repos and bundles) that are managed so they can be defined once and shared across different workflows

test bug

Bug Description

What did I do

What did I observe

What did I expect

adsadasd

To Reproduce

sadadasd

Environment

How are you running juju?

What track/channel have you deployed your charm from?

Versions of other applicable components:

Relevant log output

`juju debug-log --replay -i mycharm`

``` Paste your logs here, this'll be expandable! bla bla bla ``` `1sdasdasd`

`kubectl logs my-charm-workload`

Paste your logs here, this'll be expandable!

...

Additional context

No response

test issue using template

Bug Description

What did I do

What did I observe

What did I expect

To Reproduce

stuff

heading!

Environment

level 2 heading

Relevant log output

No response

Additional context

No response

test bug 3

Bug Description

What did I do

What did I observe

What did I expect

To Reproduce

a

Environment

How are you running juju?

What track/channel have you deployed your charm from?

Versions of other applicable components:

Relevant log output

`juju debug-log --replay -i mycharm`

Paste your logs here, this'll be expandable!  But leave a line of whitespace between the ` ``` ` and the opening/closing `<details>`
The backticks format this like code, probably making it more readable

`kubectl logs my-charm-workload`

Paste your logs here, this'll be expandable!  But leave a line of whitespace between the ` ``` ` and the opening/closing `<details>`
The backticks format this like code, probably making it more readable

Or, render shorter logs as code directly

using backticks

...

Additional context

No response

My test bug

Bug Description

What did I do

xyz

What did I observe

zyx

What did I expect

yzx

To Reproduce

1. step one
2. step two

Environment

How are you running juju?

xyz

What track/channel have you deployed your charm from?

xyz

Versions of other applicable components:

xyz

Relevant log output

juju debug-log --replay -i mycharm

my logs

kubectl logs my-charm-workload

Paste your logs here, this'll be expandable!  But leave a line of whitespace between the ` ``` ` and the opening/closing `<details>`
The backticks format this like code, probably making it more readable

Or, render shorter logs as code directly

using backticks

Additional context

n/a

test bug 2

Bug Description

What did I do

What did I observe

What did I expect

To Reproduce

sa

Environment

How are you running juju?

What track/channel have you deployed your charm from?

Versions of other applicable components:

Relevant log output

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Summary Goes Here

abc123