Skip to content

feat: use ecto schemas in models#3

Closed
efcasado wants to merge 9 commits intomasterfrom
feat-elixir-ecto-schemas
Closed

feat: use ecto schemas in models#3
efcasado wants to merge 9 commits intomasterfrom
feat-elixir-ecto-schemas

Conversation

@efcasado
Copy link
Copy Markdown
Owner

@efcasado efcasado commented May 1, 2025

No description provided.

@efcasado efcasado force-pushed the feat-elixir-ecto-schemas branch 8 times, most recently from 41367f5 to faaa55f Compare May 2, 2025 20:29
@efcasado efcasado changed the title feat: use typed ecto schemas in generated models feat: use ecto schemas in models May 3, 2025
@efcasado efcasado force-pushed the feat-elixir-ecto-schemas branch 6 times, most recently from aec6317 to d994f96 Compare May 8, 2025 18:19
@efcasado efcasado force-pushed the feat-elixir-ecto-schemas branch 4 times, most recently from d1684c7 to 21c8024 Compare May 13, 2025 07:25
@efcasado efcasado force-pushed the feat-elixir-ecto-schemas branch from 21c8024 to 6dce1e6 Compare May 13, 2025 07:28
@efcasado efcasado force-pushed the feat-elixir-ecto-schemas branch from 6dce1e6 to fa24401 Compare May 13, 2025 07:35
@efcasado efcasado force-pushed the feat-elixir-ecto-schemas branch from fa24401 to 6ad3d78 Compare May 13, 2025 07:43
@efcasado efcasado force-pushed the feat-elixir-ecto-schemas branch from f8684dc to 618e39b Compare May 13, 2025 09:04
@efcasado efcasado force-pushed the feat-elixir-ecto-schemas branch from 618e39b to 3f6e3f3 Compare May 13, 2025 09:08
@efcasado efcasado closed this May 15, 2025
efcasado pushed a commit that referenced this pull request Mar 30, 2026
…ools#21653)

* Update AWS Go SDK from v1 to v2 in Go client templates (#3)

* Initial plan

* Update AWS Go SDK from v1 to v2 in Go client templates

Co-authored-by: dennismouwen-eye <107839749+dennismouwen-eye@users.noreply.github.com>

* Final validation: AWS SDK v2 integration working correctly

Co-authored-by: dennismouwen-eye <107839749+dennismouwen-eye@users.noreply.github.com>

* Fix AWS v4 signature implementation: retrieve credentials properly from provider

Co-authored-by: dennismouwen-eye <107839749+dennismouwen-eye@users.noreply.github.com>

* Fix AWS v4 signature payload hash: properly compute SHA-256 hash for request body

Co-authored-by: dennismouwen-eye <107839749+dennismouwen-eye@users.noreply.github.com>

* Implement proper payload hashing

* Revert go.sum file to original state as requested

Co-authored-by: dennismouwen-eye <107839749+dennismouwen-eye@users.noreply.github.com>

* Revert go.mod and rename import alias from v4 back to awsv4

Co-authored-by: dennismouwen-eye <107839749+dennismouwen-eye@users.noreply.github.com>

* Revert go.mod file to original state removing all changes

Co-authored-by: dennismouwen-eye <107839749+dennismouwen-eye@users.noreply.github.com>

* Rename credentials import to awscredentials alias as requested

Co-authored-by: dennismouwen-eye <107839749+dennismouwen-eye@users.noreply.github.com>

* Fix spacing

* Fix credentials and imports

* Update aws sdk to latest version

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: dennismouwen-eye <107839749+dennismouwen-eye@users.noreply.github.com>
Co-authored-by: Dennis Mouwen <dennis.mouwen@eye.security>

* Update indenting

---------

Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
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.

1 participant