You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
** This file was automatically generated by the `build-harness`.
15
+
** This file was automatically generated by the `cloudposse/build-harness`.
18
16
** 1) Make all changes to `README.yaml`
19
17
** 2) Run `make init` (you only need to do this once)
20
18
** 3) Run`make readme` to rebuild this file.
@@ -30,29 +28,6 @@
30
28
31
29
Build Docker image and push it
32
30
33
-
---
34
-
35
-
This project is part of our comprehensive ["SweetOps"](https://cpco.io/sweetops) approach towards DevOps.
36
-
[<imgalign="right"title="Share via Email"src="https://docs.cloudposse.com/images/ionicons/ios-email-outline-2.0.1-16x16-999999.svg"/>][share_email]
37
-
[<imgalign="right"title="Share on Google+"src="https://docs.cloudposse.com/images/ionicons/social-googleplus-outline-2.0.1-16x16-999999.svg" />][share_googleplus]
38
-
[<imgalign="right"title="Share on Facebook"src="https://docs.cloudposse.com/images/ionicons/social-facebook-outline-2.0.1-16x16-999999.svg" />][share_facebook]
39
-
[<imgalign="right"title="Share on Reddit"src="https://docs.cloudposse.com/images/ionicons/social-reddit-outline-2.0.1-16x16-999999.svg" />][share_reddit]
40
-
[<imgalign="right"title="Share on LinkedIn"src="https://docs.cloudposse.com/images/ionicons/social-linkedin-outline-2.0.1-16x16-999999.svg" />][share_linkedin]
41
-
[<imgalign="right"title="Share on Twitter"src="https://docs.cloudposse.com/images/ionicons/social-twitter-outline-2.0.1-16x16-999999.svg" />][share_twitter]
42
-
43
-
44
-
45
-
46
-
It's 100% Open Source and licensed under the [APACHE2](LICENSE).
47
-
48
-
49
-
50
-
51
-
52
-
53
-
54
-
55
-
56
31
57
32
58
33
@@ -63,11 +38,8 @@ Build Docker image and push it.
63
38
64
39
65
40
66
-
67
41
## Usage
68
42
69
-
70
-
71
43
```yaml
72
44
name: Push into main branch
73
45
on:
@@ -96,6 +68,21 @@ Build Docker image and push it.
96
68
image: ${{ steps.build.outputs.image }}
97
69
tag: ${{ steps.build.outputs.tag }}
98
70
```
71
+
> [!TIP]
72
+
> If omitted, `cache-from` and `cache-to` will default to `gha`.
73
+
> In an AWS environment, we recommend using [ECR as a remote cache](https://aws.amazon.com/blogs/containers/announcing-remote-cache-support-in-amazon-ecr-for-buildkit-clients/).
@@ -111,9 +98,11 @@ Build Docker image and push it.
111
98
| build-args | List of build-time variables | N/A | false |
112
99
| cache-from | List of external cache sources for buildx (e.g., user/app:cache, type=local,src=path/to/dir) | type=gha | false |
113
100
| cache-to | List of cache export destinations for buildx (e.g., user/app:cache, type=local,dest=path/to/dir) | type=gha,mode=max | false |
101
+
| docker-metadata-pr-head-sha | Set to `true` to tag images with the PR HEAD SHA instead of the merge commit SHA within pull requests. | false | false |
114
102
| file | Dockerfile name | Dockerfile | false |
115
103
| image\_name | Image name (excluding registry). Defaults to {{$organization/$repository}}. | | false |
116
104
| login | Docker login | | false |
105
+
| no-cache | Send the --no-cache flag to the docker build process | false | false |
117
106
| organization | Organization | N/A | true |
118
107
| password | Docker password | | false |
119
108
| platforms | List of target platforms for build (e.g. linux/amd64,linux/arm64,linux/riscv64,linux/ppc64le,linux/s390x,etc) | linux/amd64 | false |
@@ -138,15 +127,6 @@ Build Docker image and push it.
138
127
<!-- markdownlint-restore -->
139
128
140
129
141
-
142
-
## Share the Love
143
-
144
-
Like this project? Please give it a ★ on [our GitHub](https://github.com/cloudposse/github-action-docker-build-push)! (it helps us **a lot**)
145
-
146
-
Are you using this project or any of our other projects? Consider [leaving a testimonial][testimonial]. =)
147
-
148
-
149
-
150
130
## Related Projects
151
131
152
132
Check out these related projects.
@@ -161,86 +141,55 @@ For additional context, refer to some of these links.
161
141
- [example-github-action-release-workflow](https://github.com/cloudposse/example-github-action-release-workflow) - Example application with complicated release workflow
162
142
163
143
164
-
## Help
165
-
166
-
**Got a question?** We got answers.
167
-
168
-
File a GitHub [issue](https://github.com/cloudposse/github-action-docker-build-push/issues), send us an [email][email] or join our [Slack Community][slack].
We are a [**DevOps Accelerator**][commercial_support]. We'll help you build your cloud infrastructure from the ground up so you can own it. Then we'll show you how to operate it and stick around for as long as you need us.
Work directly with our team of DevOps experts via email, slack, and video conferencing.
148
+
This project is under active development, and we encourage contributions from our community.
180
149
181
-
We deliver 10x the value for a fraction of the cost of a full-time engineer. Our track record is not even funny. If you want things done right and you need it done FAST, then we're your best bet.
182
150
183
-
- **Reference Architecture.** You'll get everything you need from the ground up built using 100% infrastructure as code.
184
-
- **Release Engineering.** You'll have end-to-end CI/CD with unlimited staging environments.
185
-
- **Site Reliability Engineering.** You'll have total visibility into your apps and microservices.
186
-
- **Security Baseline.** You'll have built-in governance with accountability and audit logs for all changes.
187
-
- **GitOps.** You'll be able to operate your infrastructure via Pull Requests.
188
-
- **Training.** You'll receive hands-on training so your team can operate what we build.
189
-
- **Questions.** You'll have a direct line of communication between our teams via a Shared Slack channel.
190
-
- **Troubleshooting.** You'll get help to triage when things aren't working.
191
-
- **Code Reviews.** You'll receive constructive feedback on Pull Requests.
192
-
- **Bug Fixes.** We'll rapidly work with you to fix any bugs in our projects.
193
151
194
-
## Slack Community
152
+
Many thanks to our outstanding contributors:
195
153
196
-
Join our [Open Source Community][slack] on Slack. It's **FREE** for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally *sweet* infrastructure.
Participate in our [Discourse Forums][discourse]. Here you'll find answers to commonly asked questions. Most questions will be related to the enormous number of projects we support on our GitHub. Come here to collaborate on answers, find solutions, and get ideas about the products and services we value. It only takes a minute to get started! Just sign in with SSO using your GitHub account.
201
-
202
-
## Newsletter
203
-
204
-
Sign up for [our newsletter][newsletter] that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.
205
-
206
-
## Office Hours
207
-
208
-
[Join us every Wednesday via Zoom][office_hours] for our weekly "Lunch & Learn" sessions. It's **FREE** for everyone!
Please use the [issue tracker](https://github.com/cloudposse/github-action-docker-build-push/issues) to report any bugs or file feature requests.
217
-
218
-
### Developing
219
-
220
-
If you are interested in being a contributor and want to get involved in developing this project or [help out](https://cpco.io/help-out) with our other projects, we would love to hear from you! Shoot us an [email][email].
158
+
For 🐛 bug reports & feature requests, please use the [issue tracker](https://github.com/cloudposse/github-action-docker-build-push/issues).
221
159
222
160
In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.
223
-
224
-
1. **Fork** the repo on GitHub
225
-
2. **Clone** the project to your own machine
226
-
3. **Commit** changes to your own branch
227
-
4. **Push** your work back up to your fork
228
-
5. Submit a **Pull Request** so that we can review your changes
161
+
1. Review our [Code of Conduct](https://github.com/cloudposse/github-action-docker-build-push/?tab=coc-ov-file#code-of-conduct) and [Contributor Guidelines](https://github.com/cloudposse/.github/blob/main/CONTRIBUTING.md).
162
+
2. **Fork** the repo on GitHub
163
+
3. **Clone** the project to your own machine
164
+
4. **Commit** changes to your own branch
165
+
5. **Push** your work back up to your fork
166
+
6. Submit a **Pull Request** so that we can review your changes
229
167
230
168
**NOTE:** Be sure to merge the latest changes from "upstream" before making a pull request!
231
169
170
+
### 🌎 Slack Community
232
171
233
-
## Copyright
172
+
Join our [Open Source Community](https://cpco.io/slack?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/github-action-docker-build-push&utm_content=slack) on Slack. It's **FREE** for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally *sweet* infrastructure.
Sign up for [our newsletter](https://cpco.io/newsletter?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/github-action-docker-build-push&utm_content=newsletter) and join 3,000+ DevOps engineers, CTOs, and founders who get insider access to the latest DevOps trends, so you can always stay in the know.
177
+
Dropped straight into your Inbox every week — and usually a 5-minute read.
[Join us every Wednesday via Zoom](https://cloudposse.com/office-hours?utm_source=github&utm_medium=readme&utm_campaign=cloudposse/github-action-docker-build-push&utm_content=office_hours) for your weekly dose of insider DevOps trends, AWS news and Terraform insights, all sourced from our SweetOps community, plus a _live Q&A_ that you can’t find anywhere else.
<summary>Preamble to the Apache License, Version 2.0</summary>
189
+
<br/>
190
+
<br/>
242
191
243
-
See [LICENSE](LICENSE) for full details.
192
+
Complete license is available in the [`LICENSE`](LICENSE) file.
244
193
245
194
```text
246
195
Licensed to the Apache Software Foundation (ASF) under one
@@ -260,74 +209,17 @@ KIND, either express or implied. See the License for the
260
209
specific language governing permissions and limitations
261
210
under the License.
262
211
```
263
-
264
-
265
-
266
-
267
-
268
-
269
-
270
-
212
+
</details>
271
213
272
214
## Trademarks
273
215
274
216
All other trademarks referenced herein are the property of their respective owners.
275
217
276
-
## About
277
-
278
-
This project is maintained and funded by [Cloud Posse, LLC][website]. Like it? Please let us know by [leaving a testimonial][testimonial]!
279
-
280
-
[![Cloud Posse][logo]][website]
281
-
282
-
We're a [DevOps Professional Services][hire] company based in Los Angeles, CA. We ❤️ [Open Source Software][we_love_open_source].
283
-
284
-
We offer [paid support][commercial_support] on all of our projects.
285
218
286
-
Check out [our other projects][github], [follow us on twitter][twitter], [apply for a job][jobs], or [hire us][hire] to help with your cloud strategy and implementation.
Copy file name to clipboardExpand all lines: README.yaml
+15Lines changed: 15 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -75,6 +75,21 @@ usage: |-
75
75
image: ${{ steps.build.outputs.image }}
76
76
tag: ${{ steps.build.outputs.tag }}
77
77
```
78
+
> [!TIP]
79
+
> If omitted, `cache-from` and `cache-to` will default to `gha`.
80
+
> In an AWS environment, we recommend using [ECR as a remote cache](https://aws.amazon.com/blogs/containers/announcing-remote-cache-support-in-amazon-ecr-for-buildkit-clients/).
0 commit comments