Upcoming updates to Airtable Attachment URLs that are fetched via API

[DannyMatteson-at]

Hello, I'm with the Developer Support Engineer team at Airtable and we wanted to share this upcoming notification about Changes to Airtable attachments in which Airtable will be incorporating expiring links functionality starting November 8th, 2022. I don't have full context on how gatsby-source-airtable uses these attachment URLs but more details about how this update impacts 3rd party integrations can be found in the linked support article. Please contact [email protected] with a reference to this GitHub Issue if there are any technical questions we can help address. Thanks.

[ZeldOcarina]

Oh no what a bad news..

[flogy]

Without having it tested yet, I think this can already be solved by using fileNode mappings (see: https://github.com/jbolda/gatsby-source-airtable#using-markdown-and-attachments). Like that, the attachments are downloaded at build time and made available locally. Is this correct @jbolda ?

[flogy]

Could not really get it to work so I finally switched over to gatsby-source-airtable-next which supports downloading file attachments too.

[ZeldOcarina]

Yeah I think the Gatsby team should develop an official plugin for AirTable, it's such an incredible CRM!

[jbolda]

@ZeldOcarina I have inquired multiple times in the past of Gatsby corporation would be interested in taking on ownership in the plugin, but there has never been interest.

I have attempted to find others to maintain this plugin as I am no longer involved with the community, and was doing this in my free time time, unpaid. Unfortunately, everyone has continued to fall off or not had interest in helping.

It still seems with these recent API changes, there is renewed interest in putting effort into this plugin. @davidpaulsson seems like you have an updated fork? Is there interest in maintaining and publishing under this package name? Actually separately having other conversations around pretty possible solutions, and asked in #484 if Airtable would be interested in taking an ownership interest.

[ZeldOcarina]

This has not been a breaking change for me and I am still using the plugin successfully so far. It even works with the new API tokens, you've really laid out some robust foundations here, kudos to you.
I've answered on #484 too on possible Gatsby UC involvement in this. I see it's still a small organization, but it's where I've been directed too by the Gatsby team when I asked this plugin to enter the core, too..
Not sure why they are disregarding AirTable imo it's hands down the best CRM, way better than Contentful ..

[davidpaulsson]

@jbolda It's not so much a fork but another source plugin. I'm up for maintaining and publishing under this package name, but it's a very breaking change from how this pkg works to switch to my version of sourcing from Airtable.

[jbolda]

I have decided to move this plugin over to the GUC. It seems that is the best fit for continued maintenance of this plugin.

@davidpaulsson, the adjustments that you have done seem perfectly reasonable to me. Some of that seems to stem from it's creation in a different era of Gatsby. Either way, this plugin hasn't seen any major versions for quite some time so it may very well make sense to combine efforts. I will leave that discussion to the GUC though.