Skip to content

Conversation

@Guimove
Copy link
Contributor

@Guimove Guimove commented Feb 2, 2026

AWS ElastiCache does not support configurable storage size - the capacity is determined by the node type (e.g., cache.t3.micro, cache.m6g.large). However, the UI was displaying a storage field for Redis managed databases, misleading users into thinking they could configure this value.

Changes:

  • Hide storage input field for Redis managed databases (rendered as hidden input to preserve form state)
  • Disable storage validation rules for Redis managed
  • Prevent "Apply Immediately" storage warning from appearing for Redis managed
  • Storage field remains visible and editable for other database types (PostgreSQL, MySQL, MongoDB)
  • Storage field remains visible for Redis in container mode

This fix applies to both database creation and settings update flows.

Summary

Issue:

Screenshots / Recordings

Testing

  • Changes tested locally in the relevant Console's pages and Storybooks
  • yarn test or yarn test -u (if you need to regenerate snapshots)
  • yarn format
  • yarn lint

PR Checklist

  • I followed naming, styling, and TypeScript rules (see .cursor/rules)
  • I performed a self-review (diff inspected, dead code removed)
  • I titled the PR using Conventional Commits with a scope when possible (e.g. feat(service): add new Terraform service) - required for semantic-release
  • I only kept necessary comments, written in English (watch for useless AI comments)
  • I involved a designer to validate UI changes if I am not a designer
  • I covered new business logic with tests (unit)
  • I confirmed CI is green (Codecov red can be accepted)
  • I reviewed and executed locally any AI-assisted code

AWS ElastiCache does not support configurable storage size - the capacity
is determined by the node type (e.g., cache.t3.micro, cache.m6g.large).
However, the UI was displaying a storage field for Redis managed databases,
misleading users into thinking they could configure this value.

Changes:
- Hide storage input field for Redis managed databases (rendered as hidden input to preserve form state)
- Disable storage validation rules for Redis managed
- Prevent "Apply Immediately" storage warning from appearing for Redis managed
- Storage field remains visible and editable for other database types (PostgreSQL, MySQL, MongoDB)
- Storage field remains visible for Redis in container mode

This fix applies to both database creation and settings update flows.
@RemiBonnet
Copy link
Member

Qovery Preview

Qovery can create a Preview Environment for this PR.
To trigger its creation, please post a comment with one of the following command.

Command Blueprint environment
/qovery preview 28c47145-c8e7-4b9d-8d9e-c65c95b48425 staging
/qovery preview cc1de7de-94e5-40f8-8e45-bc8986d9dfec storybook
/qovery preview {all|UUID1,UUID2,...} To preview multiple environments

This comment has been generated from Qovery AI 🤖.
Below, a word from its wisdom :

One day they will all understand

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants