AKZ AZBLOB Issues in jx-requirements.yml EnsureBucketIsCreated not implemented for LegacyBucketProvider

[michaeljohnbennett]

@chrismellard BTW we're in the process of moving to jx boot as our strategic way to install/configure/upgrade/edit Jenkins X installation, storage, networking, ingress/TLS/DNS and whatnot so if you're interested in getting storage/vault working for AKS I'd maybe start there.

with boot you can specify the URLs of the storage locations for logs in your jx-requirements.yml. I've just polished the docs around that here: https://jenkins-x.io/getting-started/boot/#storage

I think if you specify the azblob://mybucket URLs for logs in your jx-requirements.yml file it might actually work on AKS :)

But it would be nice to add an AKS implementation of this interface:

jx/pkg/cloud/factory/factory.go

Line 14 in 36cec23

return storage.NewGKEBucketProvider(requirements)

so that we can lazily create AKS buckets and verify they exist etc Usually if the user enables long term storage on GKE we let folks enter a bucket name to create and if not lazily create one etc. Would be nice to have a similar UX on AKS toto.

Originally posted by @jstrachan in #703 (comment)

I can't see this working in 2.0.1212.

When we get to verify we get this error:

Verifying Storage...
error: failed to ensure the bucket URL azblob://xxx.blob.core.windows.net/logs is created: EnsureBucketIsCreated not implemented for LegacyBucketProvider
error: failed to interpret pipeline file jenkins-x.yml: failed to run '/bin/sh -c jx step verify preinstall --provider-values-dir="kubeProviders"' command in directory '.', output: ''

Verifying the CLI packages using version stream URL: https://github.com/jenkins-x/jenkins-x-versions.git and git ref: v1.0.362
using version 2.0.1212 of jx
CLI packages kubectl, git, helm seem to be setup correctly
NAME               VERSION
jx                 2.0.1212
Kubernetes cluster v1.15.7
kubectl            v1.16.3
helm client        v2.16.3+g1ee0254
git                2.21.0 (Apple Git-120)

This happens when running jx boot

[michaeljohnbennett]

We have disable devops in the requirements and the storage part looks like this:

storage:
  backup:
    enabled: true
    url: azblob://xxx.blob.core.windows.net/backup/
  logs:
    enabled: true
    url: azblob://xxx.blob.core.windows.net/logs/
  reports:
    enabled: true
    url: azblob://xxx.blob.core.windows.net/reports/
  repository:
    enabled: true
    url: azblob://xxx.blob.core.windows.net/repistory/
vault: {}

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

[deanesmith]

Related to #7190

[chrismellard]

This PR #7451 addresses this issue by implementing the necessary half of the AKSBucketProvider, i.e.EnsureBucketIsCreated

[jenkins-x-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

[jenkins-x-bot]

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.