michaelkirkpatrick / catalog-beer-api Goto Github PK

Implement function to handle posted beer duplicates

Implement duplicate handling function

Add update capability to brewer endpoint.

Add update capability to location endpoint.

Add update capability to beer endpoint.

• Add basic SQL search capability by field name
• Add advanced SQL search capability based on free-form search string (e.g. "Google")
• Implement 3rd party search solution (e.g. Elasticsearch)

if email = validated
if email domain = brewer domain (URL)
then add permission

When I enter:
curl -X GET https://api.catalog.beer/brewer/65911cdd-52e6-6305-3420-b9bbf6ea958d -H ‘Accept: application/json' -H ‘Authorization: Basic bccf12ab-1796-4745-9e1a-f71bee61b7ec'
I get a response of:
{"error":true,"error_msg":"Missing API key. Please check that your request includes your API key as the Username using HTTP basic auth and then try again."}curl: (6) Could not resolve host: application
What am I doing wrong?

The verbose version of the response is:
Note: Unnecessary use of -X or --request, GET is already inferred.

• Trying 66.175.217.212:443...
• Connected to api.catalog.beer (66.175.217.212) port 443 (#0)
• ALPN, offering http/1.1
• successfully set certificate verify locations:
• CAfile: /opt/anaconda3/ssl/cacert.pem
  CApath: none
• TLSv1.3 (OUT), TLS handshake, Client hello (1):
• TLSv1.3 (IN), TLS handshake, Server hello (2):
• TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
• TLSv1.3 (IN), TLS handshake, Certificate (11):
• TLSv1.3 (IN), TLS handshake, CERT verify (15):
• TLSv1.3 (IN), TLS handshake, Finished (20):
• TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
• TLSv1.3 (OUT), TLS handshake, Finished (20):
• SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
• ALPN, server accepted to use http/1.1
• Server certificate:
• subject: CN=plungemasters.com
• start date: Oct 11 05:22:56 2021 GMT
• expire date: Jan 9 05:22:55 2022 GMT
• subjectAltName: host "api.catalog.beer" matched cert's "api.catalog.beer"
• issuer: C=US; O=Let's Encrypt; CN=R3
• SSL certificate verify ok.

GET /brewer/65911cdd-52e6-6305-3420-b9bbf6ea958d HTTP/1.1
Host: api.catalog.beer
User-Agent: curl/7.71.1
Accept: /

• TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
• TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
• old SSL session ID is stale, removing
• Mark bundle as not supporting multiuse
  < HTTP/1.1 401 Unauthorized
  < Date: Sun, 07 Nov 2021 21:51:42 GMT
  < Server: Apache/2.4.29 (Ubuntu)
  < Set-Cookie: PHPSESSID=logc2c6us1sseqs91blmpke26j; path=/
  < Expires: Thu, 19 Nov 1981 08:52:00 GMT
  < Cache-Control: no-store, no-cache, must-revalidate
  < Pragma: no-cache
  < Strict-Transport-Security: max-age=31415926; includeSubDomains; preload
  < Content-Length: 156
  < Content-Type: application/json
  <
• Connection #0 to host api.catalog.beer left intact
  {"error":true,"error_msg":"Missing API key. Please check that your request includes your API key as the Username using HTTP basic auth and then try again."}Note: Unnecessary use of -X or --request, GET is already inferred.
• Could not resolve host: application
• Closing connection 1
  curl: (6) Could not resolve host: application

Create a function that can check permission for:

• Add Beer
• Add Brewer
• Add Location
• Edit Beer
• Edit Brewer
• Edit Location
• Delete Beer
• Delete Location

• If a brewer is verified, allow contributors to suggest a new beer or location
• Brewers are notified via email when suggestions are made
• Brewers can then review and approve or deny suggestions
• Decisions should be relayed to the contributor who suggested the edit