💾 for integrating with external datasources

Describe the use case of your emoji

• Emoji: 💾
• Code: :floppy_disk:
• Description: “Integrate with external datasource”

We often add or remove datasources such as Elastic Search, S3 buckets, read replica databases, data streams etc.

Is this use case covered by an existing emoji?

• ➕ - This is more related to library/package dependencies
• 👽 - API != datasource
• 🗃️ - This may work for integrating with read replicas but not for other datasources
• 🧐 - This doesn’t seem right at all since this is more about investigating data

💾 could be differentiated from 🗃️ in that 💾 is more about adding or removing dependencies on “blackbox” data sources. Whereas 🗃️ is more about configuring, migrating, updating SQL queries in more of a “whitebox” way within a database. As such 💾 suggests more of an infrastructure change has occurred whereas 🗃️ is BAU database changes. The 🗃️ emoji even suggests that it’s a “whitebox” approach since it’s an open drawer.

Also note that I find 🧱 to be too general for infrastructure changes. I think it’s worth distinguishing between a limited number of types of infrastructure changes. Gitmoji IMO should remain dev focused rather devops focused. However there are useful distinctions within “infrastructure changes” for the dev work required to integrate or adapt to the infrastructure changes.

Does this emoji fall into the “how” category?

This is in the “what” category.

Examples

• 💾 Update task to store ML models in new S3 bucket
• 💾 Create consumer of the XYZ data stream
• 💾 Use new read replica for background tasks to reduce load on primary DB

[mvrangeme]

also, your issue does not follow the issue template for emoji proposal:

## Describe the use case of your emoji

<!-- Explain the creation of this emoji, what this is and when it should be used -->

### Is this use case covered by an existing emoji?

<!--
Can we cover this use case with an existing emoji? Try thinking about what
other existing emojis work similar to this and describe what are the
differences between those similar ones and this proposed one.
-->

### Does this emoji fall into the "how" category?

<!--
We are trying to always describe/categorize the "what" has been done in one
particular commit (:white_check_mark:, :lock:, :zap:...), not the "how" it was
done (the exceptions being :hankey:, :beers:). Does this emoji fall into the
"how" category?
-->

### Examples

<!--
Include some examples for using the emoji
-->

be sure to answer those questions in the issue body before we continue 🙂

Apologies. I copied the format of another issue. I guess they did it wrong as well.

Fixed now

[carloscuesta]

Agree with @vhoyer we can expand a bit the scope of the one that we have