weaveworks / weaveworks-backstage Goto Github PK

Let's look into annotating suspended resources at least with the user who is performing the operation.

Bonus points: Prompting for a reason.

Is it expected to work on custom hooks?

See useAsyncFn dependencies in useToggleSuspendResource

I tried to upgrade backstage following the user guide:
https://backstage.io/docs/getting-started/keeping-backstage-updated/

yarn backstage-cli versions:check --fix
yarn run v1.22.19

The following packages must be deduplicated by updating dependencies in package.json

 @backstage/plugin-kubernetes **@ ^0.10.2 should be changed to ^0.11.2**

The following packages can be deduplicated by updating dependencies in package.json

  @backstage/plugin-kubernetes-common @ ^0.6.5 should be changed to ^0.7.1
  @backstage/plugin-kubernetes-common @ ^0.6.6 should be changed to ^0.7.1

For now running to make it work
yarn backstage-cli versions:bump --pattern '@{weaveworksoss}/*'

Hi,

I installed the plugin as described in the README.md but I get following text displayed in the UI:

Errors:

    Request failed with 401 Unauthorized, {"error":{"name":"AuthenticationError","message":"No Backstage token"},"request":{"method":"POST","url":"/api/kubernetes/resources/custom/query"},"response":{"statusCode":401}}

Errors:

    Request failed with 401 Unauthorized, {"error":{"name":"AuthenticationError","message":"No Backstage token"},"request":{"method":"POST","url":"/api/kubernetes/resources/custom/query"},"response":{"statusCode":401}}

Errors:

    Request failed with 401 Unauthorized, {"error":{"name":"AuthenticationError","message":"No Backstage token"},"request":{"method":"POST","url":"/api/kubernetes/resources/custom/query"},"response":{"statusCode":401}}

Errors:

    Request failed with 401 Unauthorized, {"error":{"name":"AuthenticationError","message":"No Backstage token"},"request":{"method":"POST","url":"/api/kubernetes/resources/custom/query"},"response":{"statusCode":401}}

The Kubernetes plugin is configured correctly and shows information of the cluster (ServiceAccount with Cluster admin rights is set)

I include the waveworks-plugin as this into the EntityPage.tsx

const overviewContent = (
  <Grid container spacing={3} alignItems="stretch">
    {entityWarningContent}
    <Grid item md={6}>
      <EntityAboutCard variant="gridItem" />
    </Grid>
    <Grid item md={6} xs={12}>
      <EntityCatalogGraphCard variant="gridItem" height={400} />
    </Grid>

    <Grid item md={4} xs={12}>
      <EntityLinksCard />
    </Grid>
    <Grid item md={8} xs={12}>
      <EntityHasSubcomponentsCard variant="gridItem" />
    </Grid>
    <Grid container spacing={3} alignItems="stretch">
      <Grid item md={12}>
          <EntityFluxHelmReleasesCard />
      </Grid>
      <Grid item md={12}>
          <EntityFluxHelmRepositoriesCard />
      </Grid>
      <Grid item md={12}>
          <EntityFluxGitRepositoriesCard />
      </Grid>
      <Grid item md={12}>
          <EntityFluxOCIRepositoriesCard />
      </Grid>
    </Grid>
  </Grid>
);

Probably checking github-releases

There might a backstage-github-* plugin with examples of querying the github releases api w/ a token etc.

• Docs in the plugin guide, how to setup the BS proxy for the github api endpoint
• Hit it and parse out latest version
• Compare against versions in table
• Add a new column "Update available" button / link / that links out to github releases page

We should add a gitops.readOnly config option which would disable the Sync option.

https://backstage.io/docs/plugins/analytics

In addition to our Sync mechanism, we could also consider a Suspend button.

I am new to backstage, but i am able to authenticate myself and get Kubernetes resource, using service Account Token.

But when using Flux plugin, I am getting the below, Error.
Request failed with 401 Unauthorized, {"error":{"name":"AuthenticationError","message":"No Backstage token","stack":"AuthenticationError: No Backstage token\n at getEntityByReq

weave.works/suspended-comment:

Audit log ticket https://app.zenhub.com/workspaces/team-pesto-6127680175876a0014fc5657/issues/gh/weaveworks/weave-gitops-enterprise/3545

Ensure that all the cards we provide are documented in the README.

Currently we have:

FluxEntityHelmReleasesCard
FluxEntityGitRepositoriesCard
FluxEntityOCIRepositoriesCard
FluxEntityHelmRepositoriesCard

We should update the Screenshot, we only need one screenshot, perhaps of the new Deployments card.

Any plan to add support for flagger and tf controller APIs in the backstage plugin?
The plugin is great already, and these features would be an amazing addition

We should hang the sync/suspend off the Permissions framework to allow centralisation of control of these permissions.

https://backstage.io/docs/permissions/overview/

There is a small issue trying to sort resources by Updated date it uses the textual output instead of the raw date value.

See the image attached