You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a fresh install of the latest porter release (via https://porter.sh/install/), when I go to generate credentials, say, for the examples/wordpress bundle in this repo, it fails with the following:
$ porter credentials generate
Generating new credential wordpress from bundle wordpress
==> 1 credentials required for bundle wordpress
? How would you like to set credential "kubeconfig" environment variable
? Enter the environment variable that will be used to set credential "kubeconfig" foo
Saving credential to /Users/vdice/.porter/credentials/wordpress.yaml
Error: couldn't write credential file /Users/vdice/.porter/credentials/wordpress.yaml: open /Users/vdice/.porter/credentials/wordpress.yaml: no such file or directory
$ ls -haltr ~/.porter
total 88M
drwxr-xr-x 7 vdice staff 224 May 31 16:35 mixins
drwxr-xr-x 5 vdice staff 160 Jun 4 13:11 bundles
drwxr-xr-x 3 vdice staff 96 Jun 4 13:11 claims
drwxr-xr-x 7 vdice staff 224 Jun 4 13:13 .
-rwxr-xr-x 1 vdice staff 41M Jun 4 13:26 porter
-rwxr-xr-x 1 vdice staff 46M Jun 4 13:26 porter-runtime
drwxr-xr-x+ 184 vdice staff 5.8K Jun 4 13:28 ..
$ porter version
porter v0.7.0-ralpha.1+englishrose (83471fb)
It appears that the credentials sub-directory isn't auto-created... but may need to be. Does this sound like the right diagnosis?
The text was updated successfully, but these errors were encountered:
This adds a call to MkdirAll with the credentials path before we
attempt to write the credential file. This will ensure that the
credential directory exists before we try and write the file. If the
directory exists already, it's a NO-OP.
Fixesgetporter#377
* Add a call to MkdirAll for the credentials directory path.
This adds a call to MkdirAll with the credentials path before we
attempt to write the credential file. This will ensure that the
credential directory exists before we try and write the file. If the
directory exists already, it's a NO-OP.
Fixes#377
* Oopps didn't handle the error
* Cleanup test for readability
On a fresh install of the latest porter release (via https://porter.sh/install/), when I go to generate credentials, say, for the
examples/wordpress
bundle in this repo, it fails with the following:It appears that the
credentials
sub-directory isn't auto-created... but may need to be. Does this sound like the right diagnosis?The text was updated successfully, but these errors were encountered: