Skip to content

GraphQL API for updating instance amazon S3 configurations

Huzaifa Iftikhar requested to merge 423235_graphql_api_for_updating_instance_s3_config into master

What does this MR do and why?

GraphQL API for updating instance Amazon S3 configurations.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Visit GraphiQL explorer https://gdk.test:3000/-/graphql-explorer
  2. Run the following mutation to create a new AuditEvents::Instance::AmazonS3Configuration and also note down the id.
mutation createInstanceAmazonS3Configuration {
  auditEventsInstanceAmazonS3ConfigurationCreate(input: {name: "AWS S3 Sanbox Instance", awsRegion: "us-east-1", accessKeyXid: "AKIA1234AKIA1234", secretAccessKey: "SECRET123SECRET123", bucketName: "gitlab-audit-logs"}) {
    errors,
    instanceAmazonS3Configuration{
      id,
      name,
      bucketName,
      accessKeyXid,
      awsRegion
    }
  }
  1. Run AuditEvents::Instance::AmazonS3Configuration.last in rails console and verify that a new instance Amazon S3 configuration is created.
  2. Run the following graphQL query to update the above record
mutation updateInstanceAmazonS3Configuration {
  auditEventsInstanceAmazonS3ConfigurationUpdate(input: {id:"gid://gitlab/AuditEvents::Instance::AmazonS3Configuration/7", name: "AWS S3 new name", awsRegion: "us-east-1", accessKeyXid: "AKIA1234AKIANEWKEY", secretAccessKey: "NEWSECRET123SECRET321", bucketName: "audit-logs-gitlab-v2"}) {
    errors,
    instanceAmazonS3Configuration{
      id,
      name,
      bucketName,
      accessKeyXid,
      awsRegion
    }
  }
}

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #423235 (closed)

Merge request reports